chore(deps): update dependency dprint to ^0.57.0 - #135

v0.57.4

Compare Source

Changes

• fix: include wasmtime's precompile compatibility hash in the plugin cache key (#​1245)

Install

Run dprint upgrade or see https://dprint.dev/install/

Verification

These artifacts have build provenance attestations.
Verify a download with the GitHub CLI:

gh attestation verify dprint-x86_64-unknown-linux-gnu.zip --repo dprint/dprint

Checksums

v0.57.3

Compare Source

Changes

• fix: only rewrite the incremental file when new file hashes were seen (#​1244)

Install

Run dprint upgrade or see https://dprint.dev/install/

Verification

These artifacts have build provenance attestations.
Verify a download with the GitHub CLI:

gh attestation verify dprint-x86_64-unknown-linux-gnu.zip --repo dprint/dprint

Checksums

v0.57.2

Compare Source

Changes

• fix: output paths relative to the cwd in dprint incremental-state (#​1243)

Install

Run dprint upgrade or see https://dprint.dev/install/

Verification

These artifacts have build provenance attestations.
Verify a download with the GitHub CLI:

gh attestation verify dprint-x86_64-unknown-linux-gnu.zip --repo dprint/dprint

Checksums

v0.57.1

Compare Source

Changes

• fix: scan hidden directories with dprint init (#​1240)
• fix: recommend --minimum-dependency-age=0 when an older version is selected (#​1238)
• fix: accept --minimum-release-age as an alias of --minimum-dependency-age (#​1239)
• ci: generate GitHub artifact attestations (#​1067)

Install

Run dprint upgrade or see https://dprint.dev/install/

Verification

These artifacts have build provenance attestations.
Verify a download with the GitHub CLI:

gh attestation verify dprint-x86_64-unknown-linux-gnu.zip --repo dprint/dprint

Checksums

v0.57.0

Compare Source

Changes

• feat: add a shebangs config for routing extensionless scripts to a plugin (#​1230)
• feat: add --minimum-dependency-age for npm dependencies (#​1228)
• feat: add --diff-format unified to dprint check and dprint fmt --diff (#​1232)
• feat: add dprint check --json flag (#​1231)
• perf: match glob patterns on the reader threads (#​1234)
• perf: cheaper per-file plugin resolution (#​1233)

Install

Run dprint upgrade or see https://dprint.dev/install/

Checksums

v0.56.1

Compare Source

Changes

• fix: format zero files when --stdin-files is empty (#​1227)

Install

Run dprint upgrade or see https://dprint.dev/install/

Checksums

v0.56.0

Compare Source

Changes

• feat: prefer plugins on the npm registry (#​1215)
• feat: add path completion hints to CLI args (#​1217)
• feat: support formatting directory args (#​1196)
• feat: format explicit paths outside the working directory (#​1204)
• fix: keep a duplicate plugin's checksum when deduping plugin sources (#​1211)
• fix: don't duplicate a plugin specified in both a config and its extended config (#​1043) (#​1208)
• fix: apply implicit node_modules exclude and unanchored patterns in rebased scopes (#​1210)
• fix: resolve literal file and directory args without directory traversal (#​1207)
• fix: handle overflow panic in progress bars (#​1223)

Install

Run dprint upgrade or see https://dprint.dev/install/

Checksums

v0.55.2

Compare Source

Changes

• fix: build linux gnu binaries against glibc 2.17 (#​1203)

Install

Run dprint upgrade or see https://dprint.dev/install/

Checksums

v0.55.1

Compare Source

Changes

• fix(npm): resolve node_modules from config dir
  (#​1194)

Install

Run dprint upgrade or see https://dprint.dev/install/

Checksums

v0.55.0

Compare Source

dprint is a pluggable and configurable code formatting platform that unifies all your formatters.

This substantial release adds npm specifier plugins, brings dprint to many more CPU architectures, adds richer LSP support, and gives you finer-grained configuration with per-file overrides and config inheritance.

It includes two behaviour changes worth reading before you upgrade.

Highlights

• 📦 npm specifier plugins — reference plugins with npm:@scope/name@version
• 🏗️ Runs on many more architectures — Windows on ARM, Android (Termux), ppc64le, and LoongArch
• 💡 LSP completions & hover for dprint configuration files
• 🔀 dprint fmt --dirty — format only the files with uncommitted git changes
• 🎛️ Per-file plugin config overrides — apply different plugin options to specific files
• 🧬 "inherit": true for nested configuration files
• ⚠️ Plugin associations are now additive (behaviour change)
• ⚠️ Globs are now case-sensitive (behaviour change)

There's also a new website: https://dprint.dev

npm specifier plugins

You can now reference plugins via an npm: specifier in your config:

{
  "plugins": [
    "npm:@dprint/typescript@0.95.15",
    "npm:@dprint/json"
  ]
}

• Pinned form (npm:@scope/name@version) downloads and locks an exact version.
• Omitting the version (npm:@scope/name) resolves the plugin from node_modules, walking up from the config file so npm and your lockfile stay the source of truth.
• dprint add npm:@scope/name resolves the latest version and writes the pinned form, unless the package is in a nearby package.json under devDependencies, in which case the unversioned form is written, in which case node resolution will occur.

More architectures supported

dprint now runs on a much wider range of CPU architectures, including:

• Windows on ARM (aarch64-pc-windows-msvc) - Now native—previously dprint was shipping the x64 binary.
• Android / Termux.
• ppc64le.
• LoongArch (now able to run plugins).

This is made possible by migrating the Wasm plugin runtime from Wasmer to Wasmtime, with equivalent performance and a smaller dependency tree:

• Native Cranelift codegen on x86_64, aarch64, riscv64, and s390x.
• ppc64le, LoongArch, and Android compile to Wasmtime's portable Pulley bytecode (pure Rust, no native backend, no signal-based traps — which the Android sandbox doesn't allow), replacing the previous wasmi interpreter path.

LSP completions and hover for config files

dprint lsp now provides autocompletion and hover documentation when editing dprint.json / dprint.jsonc, making it easier to discover plugins and configuration options without leaving your editor.

dprint fmt --dirty

Format only the files with uncommitted changes in your git working directory — staged, unstaged, and untracked (but not gitignored):

dprint fmt --dirty

This complements the existing --staged flag.

"inherit": true for nested config files

A nested configuration file can now opt in to inheriting its ancestor's plugins and configuration. Given a config at the repo root:

// ./dprint.json
{
  "typescript": {
    "indentWidth": 4
  },
  "plugins": [
    "https://plugins.dprint.dev/typescript-0.96.1.wasm"
  ]
}

A config in a subdirectory can inherit it with "inherit": true:

// ./sub-project/dprint.json
{
  "inherit": true,
  "typescript": {
    // inherits the ancestor's TypeScript config, but overrides the indent width
    "indentWidth": 2
  }
}

• Plugins in the nested config take precedence; any not specified are inherited.
• The ancestor's includes are not inherited.
• Inheriting is opt-in so that adding a config higher in the tree doesn't unexpectedly start affecting nested configs.

Per-file plugin config overrides

Plugins now support "overrides" blocks to apply different configuration to specific files:

{
  "json": {
    "overrides": {
      "files": ["**/package.json", "**/composer.json"],
      "indentWidth": 4
    }
  }
}

Use an array for multiple overrides:

{
  "json": {
    "overrides": [
      {
        "files": ["**/package.json", "**/composer.json"],
        "indentWidth": 4
      },
      {
        "files": "**/special-package.json",
        "lineWidth": 80
      }
    ]
  }
}

Overrides are honoured consistently across CLI formatting, stdin, the editor service, the LSP, and host formatting. Note that overrides only change configuration — they don't include or exclude files.

⚠️ Plugin associations are now additive (behaviour change)

Previously, adding an "associations" glob to a plugin silently replaced the file extensions and file names it matched by default. Now associations are additive:

• A positive glob (e.g. **/*.foo) routes extra files to the plugin while its defaults keep matching.
• A negated glob (e.g. !**/*.js) cancels a default extension, file name, or path.

If you previously relied on a positive association to replace the defaults, add a negated glob to opt back out. Fixes the surprising behaviour in #​841 and #​794.

⚠️ Globs are now case-sensitive (behaviour change)

File pattern matching for includes/excludes globs is now case-sensitive (#​1082). If your patterns relied on case-insensitive matching, update them to match the actual file casing.

Read a list of files from stdin

The new --stdin-files flag reads a newline-separated list of file paths from stdin instead of from the command line arguments. It works with the fmt, check, file-paths, and format-times subcommands, which is handy when piping the output of another tool into dprint:

generate_files | dprint fmt --stdin-files

Smarter dprint init

dprint init now scans the current directory and pre-selects the plugins whose files it finds, so the defaults match your project out of the box. The plugin picker scrolls to fit your terminal and supports type-to-filter, keeping it usable even when many plugins are available.

Pass --yes (-y) to skip the prompt entirely and accept those defaults — handy for scripts and CI:

dprint init --yes

The prompt is also skipped automatically when there's no interactive terminal.

Other notable additions

• DPRINT_GLOBAL_GITIGNORE=1 — opt in to respecting git's global excludes file (core.excludesFile). Opt-in because it's machine-specific and won't exist on CI.
• NO_COLOR / FORCE_COLOR support for controlling colored output.
• dprint config update --dry-run — preview config updates without writing.
• dprint resolved-config --file <path> — show only the plugins that would format a given file.
• dprint incremental-state — print the exact signal dprint uses to decide cache reuse, so you can diff it between revisions.
• Shorter subcommand names — output-resolved-config, output-file-paths, and output-format-times are now resolved-config, file-paths, and format-times.

Changelog

Features

• feat(BREAKING): make plugin associations additive to default file matching (#​1172)
• feat(BREAKING): make globs case sensitive (#​1089)
• feat: migrate wasm plugin runtime from wasmer to wasmtime (#​1178)
• feat: add Windows on ARM (aarch64-pc-windows-msvc) builds (#​1179)
• feat: add android (Termux) builds using the wasmi interpreter backend (#​1175)
• feat: add ppc64le builds using the wasmi interpreter backend (#​1174)
• feat: use LLVM backend for LoongArch to support plugins (#​1109)
• feat: LSP completions and hover for dprint configuration files (#​1177)
• feat: support resolving plugins via npm specifiers and node resolution (#​1134)
• feat: add --dirty flag to format git working directory changes (#​1171)
• feat: add per-file plugin config overrides (#​1136)
• feat: support "inherit": true in nested configuration files (#​1160)
• feat: opt-in support for git's global excludes file via DPRINT_GLOBAL_GITIGNORE (#​1163)
• feat: support reading a list of files to format from stdin (#​1157)
• feat: support NO_COLOR and FORCE_COLOR env vars (#​1155)
• feat: add --dry-run to dprint config update (#​1156)
• feat: add --file flag to resolved-config to filter plugins by file (#​1167)
• feat: add dprint incremental-state command (#​1149)
• feat: drop output- from some subcommands (#​1150)
• feat(npm): detect plugin kind on dprint add when no path is given (#​1183)
• feat(npm): add --checksum flag to dprint add (#​1184)
• feat(init): pre-select plugins from the current directory, scrollable/filterable picker, and --yes flag (#​1185)
• feat(init): scaffold plugin config from info.json (defaultConfig + configItems) (#​1186)
• feat(init): prioritize plugin pre-selection and surface it in the list
  (#​1187)

Performance

• perf: reduce wasm plugin thread stack size to 4 MiB (#​1180)
• perf: read directories on multiple threads when globbing (#​1168)
• perf(windows): delay load DLLs not needed at startup (#​1164)
• perf: cache resolved global gitignore path to avoid repeated git subprocess (#​1165)
• perf: use similar for LSP diffing and drop dissimilar (#​1176)

Bug Fixes

• fix: normalize LSP formatted line endings to match the editor document (#​1173)
• fix: avoid hang waiting for killed process plugins in clear-cache (#​1169)
• fix: kill process plugins when running dprint clear-cache (#​1154)
• fix(npm): download binary when optional dependency is omitted (#​1161)
• fix(npm): improve musl detection (#​1145)
• fix: recompile Wasm plugin from source when loading from cache fails (#​1158)
• fix: avoid regex size limit when given many literal file paths (#​1153)
• fix: read .git/info/exclude when respecting gitignore (#​1151)
• fix(plugins): surface plugin cache cleanup errors instead of swallowing them (#​1148)
• fix(core): prevent unbounded re-evaluation when conditions oscillate (#​1137)
• fix: include plugin's resolved config in incremental cache key (#​1138)
• fix(install.sh): correct riscv64 build name, add loongarch64 support, Windows .exe path, resolve relative DPRINT_INSTALL (#​1131)

Internal

• refactor: redesign plugin cache as flat per-plugin sidecars (#​1181)

Install

Run dprint upgrade or see https://dprint.dev/install/

Checksums

v0.54.0

Compare Source

Changes

• feat: add --no-gitignore flag (#​1127)
• fix: missing windows shasum entries (#​1126, #​1128)

Install

Run dprint upgrade or see https://dprint.dev/install/

Checksums

v0.53.2

Compare Source

Changes

• fix: use original URL for plugin type detection after redirect (#​1121)

Install

Run dprint upgrade or see https://dprint.dev/install/

Checksums

v0.53.1

Compare Source

Changes

• fix: resolve relative URLs in process plugins and configs against the redirected URL (#​1114)

Install

Run dprint upgrade or see https://dprint.dev/install/

Checksums

v0.53.0

Compare Source

Changes

• feat(add): support adding multiple plugins at once (#​1102)
• feat: dprint add subcommand as alias for dprint config add (#​1101)

Install

Run dprint upgrade or see https://dprint.dev/install/

Checksums

v0.52.0

Compare Source

Changes

• fix: update to wasmer v7 (#​1096)
• fix: do not warn about failing update when plugin has no check_config_updates export (#​1087)
• fix: disable incremental formatting when using --skip-stable-format (#​1075)
• feat: dprint fmt --fail-on-change (#​1073)
• Releases are now immutable on GitHub.

Install

Run dprint upgrade or see https://dprint.dev/install/

Checksums

v0.51.1

Compare Source

Changes

• fix: prefer $HOME/.config/dprint on macOS for global config (#​1062)
  • After feedback, the dprint executable now prefers putting the global config in the folder at $HOME/.config/dprint, but will continue to use the "Application Support" macOS config directory if a config file exists in there.
• dprint is now published using trusted publishing to npm and crates.io

0.51.0 release notes: https://github.com/dprint/dprint/releases/tag/0.51.0

Install

Run dprint upgrade or see https://dprint.dev/install/

Checksums

v0.51.0

Compare Source

dprint is a pluggable, configurable code formatting platform written in Rust. It aims to unify all your code formatters in one tool.

Features

Global Configuration File

dprint now supports a global configuration file that can be used when not in a project. (#​1040)

Initialize a global config:

dprint init --global

# or
dprint config init --global

The global config location is customizable via the DPRINT_CONFIG_DIR environment variable, but by default is stored in (this reflects the update that was published in 0.51.1 after feedback):

• Linux/Mac: ~/.config/dprint/dprint.jsonc (or $XDG_CONFIG_HOME/dprint/dprint.jsonc)
  • Note: On Mac it will respect $HOME/Library/Application Support/dprint/dprint.jsonc if it exists
• Windows: %APPDATA%\dprint\dprint.jsonc

Note: You can edit the config by running dprint config edit --global

Use global config for formatting:

Once setup, the global configuration will be used by default when there's no dprint configuration file in the current directory tree; however, to prevent accidentally formatting such directories, a prompt is shown when calling dprint fmt:

> dprint fmt
Warning You're not in a dprint project. Format '/home/david' anyway? (Y/n) █

Hint: Specify the directory to bypass this prompt in the future (ex. `dprint fmt .`)

As the hint states, you can bypass the confirmation prompt by providing the current directory:

> dprint fmt .
Formatted 1 file.

To format files using only the global configuration and ignore local configuration files use:

dprint fmt --config-discovery=global

Manage global config:

# Add plugins to global config
dprint config add --global

# Update global config
dprint config update --global

# Edit global config
dprint config edit --global

Full docs: https://dprint.dev/global-config/

Improved dprint check Output

When files are not formatted, dprint check now suggests running dprint fmt to fix them, making it clearer for new users contributing to your projects what to

✂ Note

PR body was truncated to here.